this is an awesome name : D

however, I am seeing a parallel with the concept of idle-crafting I think it would be better to combine those tools into one script, and as we add more kinds of self-service autonomy, they can become features of the unified script instead of creating a new script for each one.

Would it make sense to rename idle-crafting to autonomy or i-want-it-i-do-it or something that encompasses these related ideas?

I'm not entirely sure. There obviously are parallels, but idle-crafting is (essentially) an automation tool while this one is clearly in the "gameplay" category. From the implementation perspective, I would have to think about where the synergies really are - apart from a shared main loop where units with needs get picked up. I don't see a natural place to configure this tool using an overlay.

From the communication perspective, idle-crafting has just been announced as a feature and received a lot of positive attention. I'm not sure immediately renaming it is a good idea.

From the development perspective, every need that we satisfy using a tool requires some amount of research and discussion. And other needs may require entirely different techniques. So maybe it is good to keep this thing separate for now.

Ultimately, I expect idle-crafting and related tools to be re-implemented as a C++ plugin at some point. idle-crafting currently takes about 0.7% of CPU time in my forts. Not an immediate problem, but still consuming about 7% of the total DFHack allowance. This tools time usage is hardly measurable in forts with one or two resident necromancers.

It may take until the next weekend for me to get back to this. Busy at work and other plans for the upcoming weekend.

no hurry! I have plenty of other PRs to keep me busy